---
title: Discourse
sidebarTitle: Discourse
---

import Overview from "/snippets/overview.mdx"
import PreBuiltTooling from "/snippets/generated/discourse/PreBuiltTooling.mdx"
import PreBuiltUseCases from "/snippets/generated/discourse/PreBuiltUseCases.mdx"

<Overview />
<PreBuiltTooling />
<PreBuiltUseCases />

## Access requirements
| Pre-Requisites | Status | Comment|
| - | - | - |
| Paid dev account | ❓ |  |
| Paid test account | ❓ |  |
| Partnership | ❓ | |
| App review | ❓ |  |
| Security audit | ❓ | |


## Setup guide

_No setup guide yet._

<Tip>Need help getting started? Get help in the [community](https://nango.dev/slack).</Tip>

<Note>Contribute improvements to the setup guide by [editing this page](https://github.com/nangohq/nango/tree/master/docs/integrations/all/discourse.mdx)</Note>


## Useful links

-   [Discourse API docs](https://docs.discourse.org)

<Note>Contribute useful links by [editing this page](https://github.com/nangohq/nango/tree/master/docs/integrations/all/discourse.mdx)</Note>

## API gotchas

- Discourse uses API_KEY authentication mode with `Api-Key: apiKey` and `Api-Username: API Username` in the request header to access different endpoints. Both keys can be obtained from the admin panel.
- Since Nango automatically sets the `Accept: application/json` header, there is no need to include the `.json` suffix in API endpoint URLs. For example, instead of sending a request to `/categories.json`, you can send it to `/categories`, and the JSON response will still be returned.

<Note>Contribute API gotchas by [editing this page](https://github.com/nangohq/nango/tree/master/docs/integrations/all/discourse.mdx)</Note>